OpEx: recreate the geocoded-all-cases.csv file for QGIS #5576
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…of reports to use the helper
…S. this report should generate a similar spreadsheet (with bonus new columns!)
…cations by parsing a file published by USGS which contains the lat/lon for 'Populated Places' in the USA
…at location geocoded in the static json file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Back in 2022, Mike and I generated a list of all cases starting from 2017, using the fields that were mapped on the
efcms-caseindex in elasticsearch at the time.We then fed that output into the US Census Bureau's geocoder, and generated a resulting CSV that had
lats andlons for every case, and Tenille imported that into QGIS and made some slick maps. Hooray!Now we want to refresh that data, so I tried to recreate the spreadsheet using the US Census Bureau Geocoder package from NPM.